|
In computing, the chaos model is a structure of software development. Its creator, who used the pseudonym L.B.S. Raccoon,〔http://tech.dir.groups.yahoo.com/group/scrumdevelopment/message/33620〕 noted that project management models such as the spiral model and waterfall model, while good at managing schedules and staff, didn't provide methods to fix bugs or solve other technical problems. At the same time, programming methodologies, while effective at fixing bugs and solving technical problems, do not help in managing deadlines or responding to customer requests. The structure attempts to bridge this gap. Chaos theory was used as a tool to help understand these issues.〔ACM Digital Library, (The chaos model and the chaos cycle ), ACM SIGSOFT Software Engineering Notes, Volume 20 Issue 1, Jan. 1995〕 ==Software development life cycle== The chaos model notes that the phases of the life cycle apply to all levels of projects, from the whole project to individual lines of code. * The whole project must be defined, implemented, and integrated. * Systems must be defined, implemented, and integrated. * Modules must be defined, implemented, and integrated. * Functions must be defined, implemented, and integrated. * Lines of code are defined, implemented and integrated. One important change in perspective is whether projects can be thought of as whole units, or must be thought of in pieces. Nobody writes tens of thousands of lines of code in one sitting. They write small pieces, one line at a time, verifying that the small pieces work. Then they build up from there. The behavior of a complex system emerges from the combined behavior of the smaller building blocks. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Chaos model」の詳細全文を読む スポンサード リンク
|